Syllabus Information

5.1. Methodological overview

The learning process designed for this subject is based on the following:

• The continued work from the first day of class.
• Learning concepts and methodologies for software verification and validation through lectures, in which student participation is encouraged.
• The application of such knowledge on verification and validation of software in the classes devoted to problems. In these classes, students will play an active role in the discussion of cases and solving problems.
• Classes of laboratory practices where students learn the necessary technology needed for the verification and validation of software, related with concepts and methodologies presented in lectures and problem classes.
• Teamwork, in which each team must establish and implement the test plan of a software project. Each team must submit an electronic document with such test plan and the documents generated by its application. The details of the software project will be announced in the first weeks of the course.

This course is taught only in Spanish.

5.2. Learning tasks

• In the classroom, the syllabus of the course will be developed through lectures, case analysis and problem solving, where concepts and techniques presented in the syllabus will be applied.
• The practice sessions take place in a computer lab. Throughout the different sessions, each student must do, individually or in teams, work directly related to the topics studied in the course.
• In addition, teamwork projects under the supervision of a teacher will be realized. In these projects, each team must establish the test plan of a software project and implement it.

5.3. Syllabus

• Management of the testing process
• Techniques and tools for testing
• Techniques and tools for static evaluation
• Testing and evaluation of human computer interfaces

5.4. Course planning and calendar

Schedule and presentation of works

The schedule is as follows:

• Classes in the classroom (lectures and case problems): 3 hours in an ordinary week, according to the academic calendar established by the Faculty Board. In the overall calculation of the course, approximately 2 hours per week will correspond to lectures and approximately one hour to problem solving classes.
• Laboratory classes:  one 2-hour session every two weeks, according to the academic calendar established by the Faculty Board. They are working sessions in the use of technologies for verification and validation, supervised by a teacher.
• Supervision of the teamwork.

Teamwork submission:

• The deadline for the submission of the teamwork documentation and software will be the one scheduled by the Faculty Board to hold the written exam. Interim deliveries during the course will be established and announced both in the first day of class and in the Moodle platform.

Student Work
The dedication of the student to achieve the learning outcomes in this subject is estimated at 150 hours distributed as follows:

• 60 hours, approximately, of classroom activities: lectures (30), problem solving (15) and laboratory sessions (15)
• 50 hours of team work
• 35 hours of work and actual individual study (study, problem solving, class preparation and practices, program development, etc.)
• 5 hours dedicated to the written exam and the project presentation

5.5. Bibliography and recommended resources

[BB: Bibliografía básica / BC: Bibliografía complementaria]

• [BB] 1. Koomen, T. TMap Next for result-driven testing / Koomen T., van der Aalst L., Broekman B., Vroon M.. Uitgeverij Tutein Nolthenius, Den Bosch, The Netherlands, 2006
• [BB] 2. Mazza C, Fairclough J, Melton B, Pablo DD, Scheffer A, Stevens R, Jones M, Alvisi G . Guide to Software Verification and Validation, en:Software engineering guides / [C. Mazza...(et al.)] ; edited by Jon Fairclough . - [1st. ed.] London [etc.] : Prentice Hall, 1996.
• [BB] 3. Myers, G. J. The Art of Software Testing / Myers, G. J.; Badgett, T.; Sandler, C. - 3rd Edition John Wiley and Sons Ltd, 2011
• [BC] 4. TMMi Foundation. Version 3.1. TMMi Foundation, Ireland, 2010